<html>
<head><meta charset="utf-8"><title>status of oom=panic · t-libs · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/index.html">t-libs</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/status.20of.20oom.3Dpanic.html">status of oom=panic</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="217408532"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/status%20of%20oom%3Dpanic/near/217408532" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> John Gallagher <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/status.20of.20oom.3Dpanic.html#217408532">(Nov 20 2020 at 14:39)</a>:</h4>
<p>Hi! Apologies if this isn't the right place, but I wasn't sure asking questions on <a href="https://github.com/rust-lang/rust/issues/43596">https://github.com/rust-lang/rust/issues/43596</a> would be appropriate. My company is starting to use Rust in production, and we have a very similar use  case to what's described on that issue (threads with disparate tasks, and we want OOM in one thread to not tear down the whole process). If it's currently stalled out, is there a way we could contribute to moving that implementation forward, either with programmer time or monetarily?</p>



<a name="217409247"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/status%20of%20oom%3Dpanic/near/217409247" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/status.20of.20oom.3Dpanic.html#217409247">(Nov 20 2020 at 14:44)</a>:</h4>
<p>It looks like the first step would be to implement it on nightly - probably best to comment on the tracking issue to get things moving</p>



<a name="217441147"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/status%20of%20oom%3Dpanic/near/217441147" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Amanieu <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/status.20of.20oom.3Dpanic.html#217441147">(Nov 20 2020 at 18:34)</a>:</h4>
<p>Also the standard library needs to be audited to check if all allocation points are unwind-safe and don't leak memory in case of OOM panic.</p>



<a name="217441435"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/219381-t-libs/topic/status%20of%20oom%3Dpanic/near/217441435" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steven Fackler <a href="https://rust-lang.github.io/zulip_archive/stream/219381-t-libs/topic/status.20of.20oom.3Dpanic.html#217441435">(Nov 20 2020 at 18:36)</a>:</h4>
<p>definitely before stabilization, but I don't think that would block the oom=panic implementation logic from landing on nightly</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>